docs(cli): document the new Warp Agent CLI slash commands - #493
docs(cli): document the new Warp Agent CLI slash commands#493hongyi-chen wants to merge 3 commits into
Conversation
Adds /connect-grok, /manage-billing, and /upgrade, which the docs audit flagged as new but undocumented slash commands, and fills the remaining gaps in the CLI slash command table (/fork, /reset-statusline, /status, /vim-mode) so it matches the registry in static_commands/commands.rs. Co-Authored-By: Warp Agent <agent@warp.dev>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
I'm starting a first review of this pull request. You can view the conversation on Warp. I completed the review and no human review was requested for this pull request. Comment Powered by Oz |
There was a problem hiding this comment.
Overview
This PR documents newly available Warp Agent CLI slash commands across the CLI overview, reference, configuration, model usage, input, and Grok subscription pages. The changed content aligns with the attached diff context, keeps the slash command reference consistent with the TUI command surface, and does not introduce code, configuration, or security-sensitive behavior.
Concerns
- No blocking concerns found.
- No approved or repository spec context was provided, so there is no implementation-spec drift to report.
Verdict
Found: 0 critical, 0 important, 0 suggestions
Approve
Comment /oz-review on this pull request to retrigger a review (up to 3 times on the same pull request).
Powered by Oz
…mmand - Add the /orchestrate slash command to the reference table: it is always registered for local, AI-enabled sessions on both GUI and TUI surfaces (see warpdotdev/warp app/src/search/slash_command_menu/static_commands/commands.rs). - Remove /version from the slash command table: the TUI registry test version_command_is_not_registered asserts no such command exists. warp --version remains documented under command-line flags, and the Troubleshooting > Updating section no longer references a /version slash command. Co-Authored-By: Warp Agent <agent@warp.dev>
Documents the Warp Agent CLI slash commands that the
missing_docsdrift-watch audit flagged as new-but-undocumented, plus the ones already in the registry that the CLI reference table was missing.Originating thread: https://warpdev.slack.com/archives/C09BVK0PL3Y/p1786300744335669
What changed
cli/reference.mdx— added the missing rows to the slash command table so it matchesapp/src/search/slash_command_menu/static_commands/commands.rs:/connect-grok— connect an X Premium or SuperGrok subscription (new, flagged by the audit)/manage-billing— open the team billing page (new, flagged by the audit)/upgrade— open the Warp upgrade page (new, flagged by the audit)/fork,/reset-statusline,/status,/vim-mode— already shipped and TUI-registered, but absent from a table that claims to list every slash commandcli/index.mdx— new "Checking your account, plan, and billing" section covering/status,/upgrade, and/manage-billing./manage-billingis documented as admin-only because the CLI only registers it whenmanage_billing_urlresolves for the signed-in user (app/src/terminal/input/slash_commands/data_source/tui.rs).cli/models-and-usage.mdxandagents/inference/grok-subscription.mdx—/connect-grokdocumented as the CLI shortcut into the same xAI sign-in that/api-keysexposes.cli/input-and-shell-commands.mdx— short "Vim mode" subsection for/vim-mode, which was previously only referenced indirectly through the statusline indicator.cli/configuration.mdx—/reset-statuslinenoted alongside/statusline.Verification
Availability::ALWAYS/AI_ENABLED, no feature flag) andSlashCommandSurfaces::TuiOnly, so they are GA and CLI-only.crates/warp_tui/src/terminal_session_view.rs(execute_tui_slash_command) andterminal_session_view/status_menu.rs.npm run buildpasses (364 pages).undocumented_slash_commandsfrom 3 to 0.Deferred findings from this audit run
Nothing else in this run needs a doc page, but these were triaged and deliberately left for other owners:
developers/agent-api-openapi.yaml(GET /agent/artifacts/{artifactUid}/download,GET /agent/run-by-external-reference,POST /agent/runs/{runId}/scores). They are present and non-x-internalin warp-server's canonical spec, so they belong in the published subset — but the regeneration is a wholesale rewrite that would also publish research-preview Agent Memory schemas (AgentMemoryCreateConfig,AgentAutoMemoryResponse,MemoryStoreAttachmentResponse, …) that are transitively referenced fromCreateAgentRequest/AgentResponse. Per the skill's public/private guardrail this is deferred to a dedicatedsync-openapi-specrun once that exposure is settled. Details are in the companion bookkeeping PR.style_lint. Details in the companion bookkeeping PR.Surface map and snapshot updates for this run ship in the companion audit-bookkeeping PR.
Rework changes
Addressed all findings from the adversarial review pass (rework cycle 1):
/orchestratemissing from the slash command table (IMPORTANT) — Added a row for/orchestratetocli/reference.mdx. Verified against the TUI registry (app/src/search/slash_command_menu/static_commands/commands.rs): it is unconditionally registered (commands.push(ORCHESTRATE.clone()), no feature-flag gate) withSlashCommandSurfaces::GuiAndTuiandAvailability::LOCAL | Availability::AI_ENABLED, and takes an optional[task]argument. The new row links to the existing multi-agent orchestration doc./versionincorrectly documented as a slash command (IMPORTANT) — Removed the/versionrow from the slash command table and reworded the Troubleshooting > Updating paragraph so it only points to thewarp --versioncommand-line flag. Confirmed via the TUI registry's own test,version_command_is_not_registered(app/src/search/slash_command_menu/static_commands/commands_tests.rs), which asserts no/versioncommand exists in either GUI or TUI mode.npm run preview) and captured screenshots of the full slash-commands table via computer use, confirming/orchestrateis present with the[task]argument and/versionis absent, and that the Updating section no longer mentions/version. Screenshots are attached below.Validation for this rework cycle:
npm run build(364 pages, no errors),npm run typecheck(astro check: 0 errors), and the internal link checker (3458 links, 0 broken) all pass.trunk(the repo's configuredlint/fmttool) is not installed in this sandbox, consistent with the review run.Computer-use screenshots (2)
Top of the Slash commands table on /cli/reference/, showing rows from /agent through /export-to-file.
Bottom of the Slash commands table showing /handoff through /voice, including the /orchestrate row with [task] argument.
Conversation: https://staging.warp.dev/conversation/52a9f9f7-2e0a-43ae-82c4-84a04c9d4eb1
Run: https://oz.staging.warp.dev/runs/019fdd2a-edce-719d-9dc1-678ca78ec7e0
Rework conversation: https://staging.warp.dev/conversation/0ce3f923-c90c-4034-ad80-f3b75b922650
Rework run: https://oz.staging.warp.dev/runs/019fe7e8-f2c9-79f6-b917-20360e5a448f
This PR was generated with Oz.